Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

@faec Looks like we stopped publishing crossbuild images for debian7 starting from 1.23.7. The 7.17 branch needs to stay in debian 7 because of glibc constraints. I assume once we merge elastic/golang-crossbuild#621 we should start publishing debian7 images again.

We'll likely jump into 1.24 once that is ready #43984.

@faec Looks like we stopped publishing crossbuild images for debian7 starting from 1.23.7. The 7.17 branch needs to stay in debian 7 because of glibc constraints. I assume once we merge elastic/golang-crossbuild#621 we should start publishing debian7 images again.

Ugh, I was hoping we would be able to bypass waiting for that by staying on 1.23.

/test

Hmm, it seems there are images that don't exist even after merging elastic/golang-crossbuild#621.

For example docker pull docker.elastic.co/beats-dev/golang-crossbuild:1.23.8-arm results in manifest unknown. At least we can pull the debian7 based ones now.

cc @v1v

I think we might be missing some backport here, perhaps #43026? I'm going to test it now...

For example docker pull docker.elastic.co/beats-dev/golang-crossbuild:1.23.8-arm results in manifest unknown. At least we can pull the debian7 based ones now.

There were some changes about some qemu issues, that forced us to run amr64 on arm64 workers.

That's a change done in main and the release branches but 7.17, there are some backports that need to be done:

• Don't package arm64 on amd64 workers #43026
• bk(packaging): use arm64 for darwin/arm64 #43280
• bk(dra): split arm64 for linux and darwin from amd64 #43387

Do you mind cherry-picking them in this PR and see how it goes? I don't know how the conflicts might look like, but if chery-pick is a bit complex in terms of conflicts, alternatively, it will be a matter of configuring those arm64 steps to also build on arm64.

Do you mind cherry-picking them in this PR and see how it goes? I don't know how the conflicts might look like, but if chery-pick is a bit complex in terms of conflicts, alternatively, it will be a matter of configuring those arm64 steps to also build on arm64.

Thanks, I remember the qemu issue. Yeah, I'll try to cherry pick them and see if that solves the issue.

@v1v Unfortunately, I couldn't get things to work. To experiment with the backports, I opened a separate PR at #44643. There were too many conflicts when cherry-picking the original PRs, so I decided to apply the changes manually. I may have messed something up (which is quite likely), or we might still be missing some backports. Would you mind taking a look? We might need someone more experienced with the Buildkite pipelines to get this working.

Would you mind taking a look? We might need someone more experienced with the Buildkite pipelines to get this working

Please see my comment:

• DO NOT MERGE - Testing 7.17 backports #44643 (comment)

For cross-reference, the pipeline issues are fixed in #44701.

@faec Can you update heartbeat/Dockerfile? Thanks

--- a/heartbeat/Dockerfile
+++ b/heartbeat/Dockerfile
@@ -1,4 +1,4 @@
-FROM golang:1.23.6
+FROM golang:1.23.8

 RUN \

Closing in favour of #43984